Add TYPE_USE to @NonNull for type-use annotation support #35289
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This allows @nonnull to be used in type-use positions (such as generic type parameters and return types), in addition to methods, parameters, and fields. This enables broader compatibility with modern null-safety tools and aligns with common usage in the Java ecosystem. Signed-off-by: yuvarajapril91 <[email protected]>
spring-projects-issues
added
the
status: waiting-for-triage
|
This type is now deprecated in favor of JSpecify annotations. We don't intend to evolve this as a result. |
bclozel
added
status: declined
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
This PR adds
ElementType.TYPE_USEto the@Targetannotation for@NonNull, enabling it to be used in type-use positions (such as generic type parameters and return types) in addition to methods, parameters, and fields. This supports modern null-safety tooling and aligns with best practices in the Java ecosystem.Javadoc has been updated to reflect this expanded usage.
Checklist
mainbranch